Mobile Device, Method, and Computer Storage Medium for Determining an Order of Stored Data Items/Payment Account Numbers Based on Location

ABSTRACT

A mobile device having: a position determination device configured to determine a location of the mobile device; a transceiver configured to communicate with a transaction terminal via near field communication; a communication device configured to communicate with at least one server over internet; a memory storing a plurality of data items and a set of instructions of a mobile application; and at least one microprocessor coupled with the memory to execution the instructions of the mobile application. The mobile application is configured to: communicate the location of the mobile device, using the communication device, to the at least one server over internet; determine, via communications with the at least one server based on the location of the mobile device, an order of data items; and communicate, using the transceiver via near field communication, with the transaction terminal in accordance with the order of the data items.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/363,339, filed Mar. 25, 2019, which is a continuation of U.S. patentapplication Ser. No. 15/587,289, filed May 4, 2017, now U.S. Pat. No.10,282,723, issued May 7, 2019, which is a continuation of U.S. patentapplication Ser. No. 14/984,762, filed Dec. 30, 2015, now U.S. Pat. No.9,672,511, issued Jun. 6, 2017, which claims the benefit of U.S.Provisional Patent Application No. 62/098,054, filed Dec. 30, 2014, thedisclosures of which are hereby incorporated by reference in theirentireties.

The present application relates to U.S. Pat. App. Pub. Nos.2009/0112766, 2013/0024371, 2010/0211445, and 2005/0071225, and2005/0071227, the entire disclosures of each of which are herebyincorporated by reference in their entireties.

FIELD OF THE TECHNOLOGY

At least some embodiments disclosed herein relate to location dependentoperations of computing devices.

BACKGROUND

Many technologies have been developed to determine, in real time, thecurrent location of a device. For example, satellites in the globalpositioning system (GPS) transmit radio frequency signals from differentpositions in the space; and a GPS receiver receives the signals from thesatellites and determines its position from the timing differences ofthe received signals. For example, a cellular communication device candetermine or estimate its location based on cellular communicationsignals from basestations. For example, a wireless communication devicecan be configured to compute its location based on signals from awireless communication access point.

The availability of location information of a mobile device allows thedevelopment of various location dependent services. For example, U.S.Pat. App. Pub. No. 2001/0027422 discloses a system configured to pay forlocation dependent services using a cellular phone as a payment device,where a service location provides a user requested service or goodsbased on the approximate geographical position of the cellular phone.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments are illustrated by way of example and not limitation inthe figures of the accompanying drawings in which like referencesindicate similar elements.

FIG. 1 shows a system configured to facilitate location dependentcommunications between mobile devices and transaction terminalsaccording to one embodiment.

FIG. 2 shows a system to present account information according to oneembodiment.

FIG. 3 shows a method to process a payment based on a location of amobile device according to one embodiment.

FIG. 4 shows an electronic payment processing system according to oneembodiment.

FIG. 5 illustrates a transaction terminal according to one embodiment.

FIG. 6 illustrates an account identifying device according to oneembodiment.

FIG. 7 illustrates a data processing system according to one embodiment.

DETAILED DESCRIPTION

FIG. 1 shows a system configured to facilitate location dependentcommunications between mobile devices and transaction terminalsaccording to one embodiment.

In FIG. 1, the system is configured to optimize, based on the locationof the mobile device (201), the communication between a mobile device(201) of a user (101) and transaction terminals (105). The transactionterminals (105) are connected to a network (265); and the mobile device(201) is capable of communicating separately with the transactionterminals (105) and at least one remote server (228) that may or may notbe connected to the network (265).

The mobile device (201) is configured to use the position determinationdevice (263) to determine its current position. For example, theposition determination device (263) of one embodiment is a GPS receiverconfigured to receive GPS signals (269) from GPS satellites (e.g., 267)and/or similar signals from basestations. Other position determinationtechniques can also be used. For example, the position determinationdevice (263) of one embodiment is configured to determine its positionbased on signals from basestations (e.g., 109) for cellularcommunications, and/or signals from access points of wireless local areanetworks (WLAN).

In FIG. 1, in preparation for a communication session with one of thetransaction terminals (105), the mobile device (201) is configured tocommunicate with the server (228) to sort or adjust the order of thedata items based on the current location of the mobile device (201).Optionally, the mobile device (201) may present a user interface thatallows the user (101) to view the adjusted order and/or further manuallyadjust the order through the user interface. In the communicationsession, the mobile device (201) is configured to present the data items(261) in that order that is optimized based at least in part on thelocation of the mobile device (201) and thus reduces the duration of thecommunication session and/or the user effort on the user interface todirect the communications between the mobile device (201) and therespective one of the transaction terminals (105).

In one embodiment, the mobile device (201) is configured to have atleast two wireless communication transceivers: a shorter rangetransceiver (111) for communication with one of the transactionterminals (105) that is in close proximity to the mobile device (201)(e.g., via Near Field Communication (NFC)); and, a longer rangetransceiver (113) for communication with a remote server (228) (e.g.,via cellular telecommunications, WiFi/wireless local area network).

Periodically, the mobile device (201) of one embodiment communicateswith the server (228) via the longer range transceiver (113) to adjustthe order of the data items such that the order of the data items isoptimized for a potential communication session with a transactionterminal (105) in the vicinity of the mobile device (201) using theshorter range transceiver (111).

For example, the mobile device (201) transmits its current geographicallocation, computed by the position determination device (263), using thelonger ranger transceiver (113) to the server (228). In response, theserver (228) identifies a category based on the location received fromthe mobile device (201) and communicates the category to the mobiledevice (201), which adjusts the order of the data items (261) accordingto the category. In some embodiments, the mobile device (201) postponesthe adjustment of the order until a communication session with atransaction terminal (105) is about to be initiated using the shorterranger transceiver (111), or during the initiation of the communicationsession with the transaction terminal (105).

For example, the server (228) is configured to store data identifyingthe categories (107) of different transaction terminals (105) arrangedat different locations. Based on the current location of the mobiledevice (201), the server (228) is configured to identify one or moretransaction terminals (105) that are closest to the current location ofthe mobile device (201) and determine a category of a transactionterminal (105) with which the mobile device (201) is most likely toinitiate a communication session at or near the location reported bymobile device (201). In one embodiment, the most likely transactionterminal is determined further based on the communication history of themobile device (201) with different transaction terminals. Since themobile device (201) stores the data items (261) with priority preferenceinformation in association with various categories, the prioritycategory identified by the server (228) allows the mobile device (201)to adjust and/or update the priority order of the data items (261).

In one embodiment, the mobile device (201) monitors its current locationdetermined by the position determination device (263). When the currentlocation of the mobile device (201) has changed significantly from thelocation previously communicated to the server (228) (e.g., relative tothe average spacing of transaction terminals in the area), the mobiledevice (201) communicates with the server (228) to obtain an update forthe category used to optimize the order of the data items (261). Thus,the communications with the server (228) can be reduced.

In some embodiments, after determining the priority category based onthe current location of the mobile device (201), the server (228) isconfigured to further identify the optimized order of the data items(261) and communicate the updated order to the mobile device (201), withor without explicitly identifying the priority category to the mobiledevice (201).

In one embodiment, optimizing the order of the data items (261) includesselecting a top-ranked data item to be communicated first to atransaction terminal (105). The mobile device (201) of one embodiment isconfigured with a user interface that allows the user (101) tooptionally view an identification of the top-ranked data item prior tothe mobile device (201) communicating the top-ranked data item to atransaction terminal (105). Using the user interface the user (101) mayoptionally select a different data item for communicating to thetransaction terminal (105). The optimization of the order of the dataitems (261) can reduce the need that the user optionally using the userinterface for viewing the top-ranked data item and/or select a differentdata item to replace the top-ranked data item. In one embodiment, theuser inputs made via the user interface are further tracked and used inthe optimization of the order of the data items (261) to minimize futureuser inputs.

The technique discussed above can be used to optimize the presentationof account numbers from a mobile wallet to a transaction terminal. Forexample, the data items (261) may be account numbers of payment accountsin a mobile wallet configured in the mobile device (201). Differentpayment accounts may offer different benefits for payments made forpurchases in different merchant categories. Based on the merchantcategories of the transaction terminals (105) connected in the network(265) (e.g., an electronic payment processing network illustrated inFIG. 4), the server (228) (e.g., a portal of the network (265)) isconfigured to use the location reported by the mobile device (201)(and/or other information, such as data recording the past transactionsmade in the payment accounts configured in the mobile wallet) toidentify a merchant category for prioritization, allowing the mobiledevice (201) to re-arrange the order of the account numbers in themobile wallet to present first the account number that can potentiallyprovide the best benefits to the payment transaction to be made on atransaction terminal (105) that is in close proximity to the mobiledevice (201). For example, the mobile wallet may present a userinterface to identify the top ranked payment account for confirmation bythe user in the transaction with the nearby transaction terminal (105).For example, the mobile wallet may use the top ranked payment account asthe default account for the transaction with the nearby transactionterminal in absence of user input. For example, the mobile wallet mayuse the payment accounts sequentially according to the optimized orderto process the payment until the payment is satisfied.

Mobile payment wallet services, such as Apple Pay and Google Wallet,allow a user (101) to store multiple credit cards on a mobile device(201).

In one embodiment, a mobile wallet application is configured to usegeolocation to determine the order of the credit cards (and/or otherpayment accounts, such as debit cards, prepaid cards) in which thepayment accounts are presented to make a payment at a transactionterminal, such as a point of sales terminal of a merchant.

For example, the mobile wallet may use the top ranked payment account tomake the payment without the user having to manually select a paymentaccount from the plurality of payment accounts configured in the mobilewallet. Optionally, the mobile wallet may show the sorted list ofpayment accounts to allow the user to select a payment account to makethe payment at the point of sales terminal of the merchant.

In one embodiment, the order of the credit cards is determined beforethe mobile wallet is used to make a payment and/or before the mobilewallet communicates with the points of sales terminal to reduce theprocessing/waiting time at the point of sales terminal. For example, inresponse to a determination that the mobile device is having a locationinside a retail location, the mobile wallet may optimize the order basedon reward optimization and/or user preferences.

For example, in one embodiment, the mobile wallet is configured todetermine the type of the merchant of the retail store in which themobile device is currently and determine which payment card is to beautomatically selected at the time of purchase, checkout, or payment.

In some embodiments, the mobile wallet is further configured to identifythe loyalty programs acceptable the point of sales terminal of themerchant and communicate information from the mobile wallet to the pointof sales terminal to identify the member information of the user of themobile wallet. For example, a point of sales terminal of a merchant mayaccept the phone number of the user as an identifier of a member in thereward program of the merchant. For example, a point of sales terminalof a merchant may accept a member ID of the user issued by the merchantto the user in the reward program of the merchant. In one embodiment,the reward membership information is transmitted to the point of salesterminal of the merchant prior to, or together with, the paymentinformation that identifies a payment account of the user. In oneembodiment, the payment information is a token or a one-time accountthat represents, or is associated with, the payment account of the user.

For example, loyalty programs associated with payment cards may providerewards of different levels for payments with merchants of differenttypes. For example, the loyalty program of one card may offer betterrewards on gas purchases than restaurant purchases. For example, a usermay prefer to use a particular payment card to make one type ofpurchases and another payment card to make another type of purchases,for reasons may or may not related to rewards. In one embodiment, themobile wallet is configured to determine the merchant type based on thelocation coordinates of the mobile device and then automatically rankthe payment accounts based on predicted rewards benefits and/or userpreferences.

In one embodiment, when the mobile wallet is used to make a payment atthe point of sales terminal of a merchant, the mobile wallet uses thetop ranked payment account. Alternatively or in combination, the mobilewallet may provide a user interface that allows the user to reject theuse of the top ranked payment account and/or select an alternativepayment account. The ranking according to the optimization of the rewardbenefits and/or pre-specified user rules can reduce and/or eliminate theneed for user intervention to select a payment account from the mobilewallet and thus reduce the time at the point of sales terminal andimprove the overall efficiency of the payment system.

In one embodiment, the mobile wallet application will automaticallyselect the better rewards card to use depending on the identity of themerchant determined based on the location of the mobile device.

In one embodiment, after multiple payment cards are configured and/orstored in a mobile wallet on the mobile device, the mobile wallet allowsthe user to select the option of using a default card to make payments.In one embodiment, the default card is dynamically determined based onlocation coordinates of the mobile device.

For example, in one embodiment, for one or more of the payment cards,the mobile wallet presents a user interface allowing the user to specifymerchant attributes, such as merchant types (e.g., gas, drug store,restaurant), etc., such that when the current location of the mobiledevice is determined to have the merchant attributes specified for thecorresponding payment card, the mobile application is configured toidentify the corresponding payment card as the default card for thecurrent location.

In one embodiment, when the merchant attribute determined for thecurrent location satisfies none of the payment cards in the mobilewallet, a predetermined card is selected as the default card.

In one embodiment, when the merchant attribute determined for thecurrent location satisfies more than one of the payment cards in themobile wallet, the payment cards are ranked based on prior selectionhistories and the reward rules of the reward programs associated withthe payment cards.

For example, the issuers of the payment cards may communicate the latestrewards information to the mobile wallet application. The reward programof a payment card may specify rewards as different percentage oftransaction amounts based on different merchant types corresponding todifferent merchant category codes; and the association of the rewardpercentages with respective merchant categories may change periodically(e.g., monthly, quarterly). Using the reward percentage informationand/or user preferences, the mobile wallet application is configured todynamically rank the payment accounts in a preferred order for makingpayments. Thus, the user does not have to manually select a default cardfor a particular combination of merchant attributes.

The feature of the mobile wallet to dynamically rank the paymentaccounts configured in the mobile wallet would prompt competition amongissuers and/or loyalty programs to offer better rewards than theircompetitors in order to become the “top of the wallet” credit card.

In one embodiment, a location determination system of the mobile device,such as a global positioning system (GPS) receiver in a smart phone, canbe used to determine the location coordinates of the current location ofthe mobile device and thus look up the merchant and correspondingmerchant attributes based on the location coordinates.

For example, the geolocation feature on a smart phone can determine themerchant at the current location of the smart phone; and a databasestored in the cloud can be used to determine the merchant type of themerchant.

In one embodiment, the mobile wallet is configured to weigh the rewardbenefits predicated based on the merchant category of the currentlocation and preferences of the users to compute a score for each of thepayment accounts. The scores of the payment accounts are used to rankthe payment accounts in the mobile wallet. The mobile wallet allows theuser to select payment accounts for the dynamically sorted list ofpayment accounts to make a payment. The user selection is used with amachine learning technique to train the weights in the computation ofthe scores and thus reflect the user preference. Over a period of time,the mobile wallet is capable of presenting payment accounts in desirableorders that reflects both the optimization of reward benefits and userpreferences. Thus, the accuracy of the top ranked payment card formaking a payment at a location is improved.

In one embodiment, the mobile device is configured to automaticallyretrieve reward rules from issuers of the payment accounts and/or therespective loyalty program providers.

FIG. 2 shows a system to present account information according to oneembodiment. In FIG. 2, the mobile device (201) has a GPS receiver (211)configured to determine the location coordinates (221) of the currentlocation of the mobile device (201). The mobile device (201) has atleast one internet access interface (203) for communication with remoteservers. Examples of such an internet access interface (203) include acellular communications transceiver, a wireless local area networktransceiver, etc.

In FIG. 2, a geolocation server (223) provides Application ProgrammingInterfaces (API) that allow the mobile wallet (213), implemented as amobile application executed by the microprocessor (209) in the mobiledevice (201), to submit location coordinates (221) of the currentlocation of the mobile device (201) and retrieve various informationabout that location, such as the name and address (225) of a merchantthat contains the location.

For example, APIs of Google Places accept the latitude and longitude asinputs to obtain the name and address of the business at the location.

In FIG. 2, a merchant attribute server (227) stores a table to look upthe merchant attribute (229), such as the merchant category code (MCC)of the merchant identified by the merchant name and address (225).

For example, APIs of Visa Supplier Locator can provide the MCC of 5541and 5542 for “Shell Oil” and “2901 S NORFOLK ST SAN MATEO Calif. 94403”.

In FIG. 2, the mobile wallet (213) stores a set of data identifyingpayment accounts (251, 253, . . . , 257).

In one embodiment, the mobile wallet (213) has a user interface (205)that allows the user (101) to specify, for each of the accounts (251,253, . . . , 257), a merchant category code group. For example, the userinterface (205) provides options such as “gas” and “grocery stores”. Theuser may select the “gas” group of merchant category code for Account A(251), and the “grocery stores” group of merchant category code forAccount B (253).

In one embodiment, the user interface (205) is configured to allow theuser to select an account (e.g., 257) as a default account and thusbeing associated with all merchant categories. When the mobile wallet(213) is used at a location having a merchant category code that is notassociated with other accounts (e.g., 251, 253, . . . ), the defaultaccount is considered a match.

In one embodiment, the user selection of the merchant category codegroups for association with the accounts (e.g., 251, 253, . . . , 257)represents the user preferences of the accounts. For a given set ofmerchant category codes associated with the current location of themobile device (201), the mobile wallet (213) is configured to determinematching scores of the accounts (251, 253, . . . , 257) configured inthe mobile wallet. In one embodiment, the more merchant category codesan account has that do not match with the merchant category codesassociated with the current location, the lower the matching score ofthe account for the current location.

In one embodiment, the mobile wallet is configured to periodicallyretrieve from the loyalty programs and/or issuers of the accounts (251,253, . . . , 257) the reward rules (215).

For example, the Chase's Freedom Card offers a promotion where, forthree months, restaurant purchases would earn 5% cash back. The mobilewallet associates the account (251) with the merchant category (217)(e.g., restaurant) and with the reward scale (291) (e.g., 5% cash back)as part of the reward rules (215).

In one embodiment, the matching score includes the weight of the rewardscale. For example, the higher the reward scale, the larger is the addedweight for matching with the merchant category of the account (e.g.,251).

In one embodiment, when a user (101) selects a merchant category group(217) for association with an account (251), the user interface (205)allows the user (101) to specify a reward scale (291). The reward scale(291) quantifies the user preference, which can be compared with thecorresponding reward scales (219) of reward rules. Thus, the userpreference and the reward rules can be considered in a unified matchingscore.

Further, in one embodiment, the mobile wallet is configured to adjustthe user specified reward scale (219) according to usage patterns of themobile wallet to optimize the scoring to improve the accuracy inpredicting the payment account the user (101) would like to use at alocation of a given set of merchant category codes.

In one embodiment, after the determination of the merchant attribute(229) (e.g., merchant category codes) for the location determined by theGPS receiver (211), the mobile wallet (213) sorts and/or selects a topmatching account (e.g., 251) as the “top of the wallet” account.

For example, in FIG. 2, the mobile device (201) includes an NFCtransceiver (207) to communicate account information (142) to the NFCreader/transceiver (231) of the transaction terminal (105) of themerchant to make the payment using the account information (42) thatidentifies the “top of the wallet” account.

In one embodiment, the user interface (205) is configured to optionallyshow the list of sorted accounts and allow the user to select an accountfor the payment transaction at the current location, before the mobilewallet (213) communicates the account information (142) to thetransaction terminal (105). If the “top of the wallet” account is notselected, the mobile wallet (213) adjusts the reward preference (215)(e.g., via a machine learning technique) to improve the accuracy inpredicting the “top of the wallet” account. Thus, over a period of time,the accuracy of predictions of the mobile wallet become satisfactory;and the user may simply use the mobile wallet (213) to make the paymentusing the “top of the wallet” account identified by the mobile wallet(213), without requesting a view of the list accounts (251, 253, . . . ,257) that is dynamically ordered according to the merchant categorycodes of the location coordinates (221) determined by the GPS receiver(211).

In FIG. 2, the transaction terminal (105) is connected to an electronicpayment processing network, which includes an acquirer processor (147)controlling the merchant account (148) and the issuer processor (146)controlling the consumer account (146) identified by the accountinformation (142). The transaction handler (103) interconnects theissuer processors (e.g., 145) and the acquirer processors (e.g., 147) inthe electronic payment processing network.

FIG. 3 shows a method to process a payment based on a location of amobile device according to one embodiment. For example, the method ofFIG. 3 can be implemented in the system of FIG. 2.

In FIG. 3, a computing apparatus is configured to: store (241) accountinformation of a plurality of payment accounts in a mobile device; store(243) data identifying merchant category based rules of rewards formaking payments using the accounts; determine (245) location coordinatesof the mobile device using a GPS receiver; determine (247) a merchantcategory associated with the location coordinates; rank (249) thepayment accounts in an order based on reward benefits predicted based onthe merchant category; and process (251) a payment at the location basedon the order of the payment accounts.

In one embodiment, the mobile device (201) is configured toautomatically communicate member ID of the user in a merchant loyaltyprogram to the POS during the payment processing and thus eliminates theneed to separately identify the membership (e.g., by swiping the loyaltycard from the merchant, or entering the phone number of the user toindicate the membership).

In one embodiment, payment accounts in a mobile wallet implemented in amobile device are sorted and selected for payment transactions based onthe location coordinates determined by the location determination systemof the mobile device. For example, after the global positioning system(GPS) receiver of the mobile device determines its current locationcoordinates, the mobile device is configured to determine one or moreattributes associated with the location coordinates. A set of rules areapplied to score the payment accounts based on the attributes and sortthe payment accounts in the mobile wallet based on the scores. When themobile wallet is used to make a payment, the payment accounts arepresented in the sorted order for making the payment.

FIG. 4 shows an electronic payment processing system according to oneembodiment.

In FIG. 4, the transaction handler (103) is coupled between an issuerprocessor (145) in control of a consumer account (146) and an acquirerprocessor (147) in control of a merchant account (148). An accountidentification device (141) is configured to carry the accountinformation (142) that identifies the consumer account (146) with theissuer processor (145) and provide the account information (142) to thetransaction terminal (105) of a merchant to initiate a transactionbetween the user (101) and the merchant.

FIGS. 5 and 6 illustrate examples of transaction terminals (105) andaccount identification devices (141). FIG. 7 illustrates the structureof a data processing system (170) that can be used to implement, withmore or fewer elements, at least some of the components in the system,such as the transaction handler (103), the portal (143), the datawarehouse (149), the account identification device (141), thetransaction terminal (105), etc.

In one embodiment, the financial transactions are made via an accountidentification device (141), such as financial transaction cards (e.g.,credit cards, debit cards, banking cards, etc.); the financialtransaction cards may be embodied in various devices, such as plasticcards, chips, radio frequency identification (RFID) devices, mobilephones, personal digital assistants (PDAs), etc.; and the financialtransaction cards may be represented by account identifiers (e.g.,account numbers or aliases). In one embodiment, the financialtransactions are made via directly using the account information (142),without physically presenting the account identification device (141).

In one embodiment, the transaction handler (103) couples with acentralized data warehouse (149) organized around the transaction data.For example, the centralized data warehouse (149) may include, and/orsupport the determination of, spend band distribution, transaction countand amount, merchant categories, merchant by state, cardholdersegmentation by velocity scores, and spending within merchant target,competitive set and cross-section.

For example, the centralized data warehouse (149) may includeadvertisement data and/or offers of benefits such as discount, reward,points, cashback, etc. The offers can be communicated to the users(e.g., 101) via the portal (143) or other communication channels.

In one embodiment, the centralized data warehouse (149) providescentralized management but allows decentralized execution. For example,a third party strategic marketing analyst, statistician, marketer,promoter, business leader, etc., may access the centralized datawarehouse (149) to analyze customer and shopper data, to providefollow-up analyses of customer contributions, to develop propensitymodels for increased conversion of marketing campaigns, to developsegmentation models for marketing, etc. The centralized data warehouse(149) can be used to manage advertisement campaigns and analyze responseprofitability.

In one embodiment, the centralized data warehouse (149) includesmerchant data (e.g., data about sellers), customer/business data (e.g.,data about buyers), and transaction records (301) between sellers andbuyers over time. The centralized data warehouse (149) can be used tosupport corporate sales forecasting, fraud analysis reporting,sales/customer relationship management (CRM) business intelligence,credit risk prediction and analysis, advanced authorization reporting,merchant benchmarking, business intelligence for small business,rewards, etc.

Transaction Processing and Data

FIG. 4 shows an electronic payment processing system according to oneembodiment.

In FIG. 4, the transaction handler (103) is coupled between an issuerprocessor (145) and an acquirer processor (147) to facilitateauthorization and settlement of transactions between a consumer account(146) and a merchant account (148). The transaction handler (103)records the transactions in the data warehouse (149).

The portal (143) is configured to communicate with user devices outsidethe electronic payment processing network. The portal (143) may beimplemented as a web portal, a telephone gateway, a file/data server,etc.

In FIG. 4, the transaction terminal (105) initiates the transaction fora user (101) (e.g., a customer) for processing by a transaction handler(103). The transaction handler (103) processes the transaction andstores transaction data about the transaction, in connection withaccount data, such as the account profile of an account of the user(101). The account data may further include data about the user (101),collected from issuers or merchants, and/or other sources, such associal networks, credit bureaus, merchant provided information, addressinformation, etc. In one embodiment, a transaction may be initiated by aserver (e.g., based on a stored schedule for recurrent payments).

The accumulated transaction data and the corresponding account data areused to generate intelligence information about the purchase behavior,pattern, preference, tendency, frequency, trend, amount and/orpropensity of the users (e.g., 101), as individuals or as a member of agroup. The intelligence information can then be used to generate,identify and/or select targeted advertisements for presentation to theuser (101), during a transaction, after a transaction, or when otheropportunities arise.

In FIG. 4, the consumer account (146) is under the control of the issuerprocessor (145). The consumer account (146) may be owned by anindividual, or an organization such as a business, a school, etc. Theconsumer account (146) may be a credit account, a debit account, or astored value account. The issuer may provide the consumer (e.g., user(101)) an account identification device (141) to identify the consumeraccount (146) using the account information (142). The respectiveconsumer of the account (146) can be called an account holder or acardholder, even when the consumer is not physically issued a card, orthe account identification device (141), in one embodiment. The issuerprocessor (145) is to charge the consumer account (146) to pay forpurchases.

The account identification device (141) of one embodiment is a plasticcard having a magnetic strip storing account information (142)identifying the consumer account (146) and/or the issuer processor(145). Alternatively, the account identification device (141) is asmartcard having an integrated circuit chip storing at least the accountinformation (142). The account identification device (141) mayoptionally include a mobile phone having an integrated smartcard.

The account information (142) may be printed or embossed on the accountidentification device (141). The account information (142) may beprinted as a bar code to allow the transaction terminal (105) to readthe information via an optical scanner. The account information (142)may be stored in a memory of the account identification device (141) andconfigured to be read via wireless, contactless communications, such asnear field communications via magnetic field coupling, infraredcommunications, or radio frequency communications. Alternatively, thetransaction terminal (105) may require contact with the accountidentification device (141) to read the account information (142) (e.g.,by reading the magnetic strip of a card with a magnetic strip reader).

The transaction terminal (105) is configured to transmit anauthorization request message to the acquirer processor (147). Theauthorization request includes the account information (142), an amountof payment, and information about the merchant (e.g., an indication ofthe merchant account (148)). The acquirer processor (147) requests thetransaction handler (103) to process the authorization request, based onthe account information (142) received in the transaction terminal(105). The transaction handler (103) routes the authorization request tothe issuer processor (145) and may process and respond to theauthorization request when the issuer processor (145) is not available.The issuer processor (145) determines whether to authorize thetransaction based at least in part on a balance of the consumer account(146).

The transaction handler (103), the issuer processor (145), and theacquirer processor (147) may each include a subsystem to identify therisk in the transaction and may reject the transaction based on the riskassessment.

The account identification device (141) may include security features toprevent unauthorized uses of the consumer account (146), such as a logoto show the authenticity of the account identification device (141),encryption to protect the account information (142), etc.

The transaction terminal (105) of one embodiment is configured tointeract with the account identification device (141) to obtain theaccount information (142) that identifies the consumer account (146)and/or the issuer processor (145). The transaction terminal (105)communicates with the acquirer processor (147) that controls themerchant account (148) of a merchant. The transaction terminal (105) maycommunicate with the acquirer processor (147) via a data communicationconnection, such as a telephone connection, an Internet connection, etc.The acquirer processor (147) is to collect payments into the merchantaccount (148) on behalf of the merchant.

In one embodiment, the transaction terminal (105) is a POS terminal at atraditional, offline, “brick and mortar” retail store. In anotherembodiment, the transaction terminal (105) is an online server thatreceives account information (142) of the consumer account (146) fromthe user (101) through a web connection. In one embodiment, the user(101) may provide account information (142) through a telephone call,via verbal communications with a representative of the merchant; and therepresentative enters the account information (142) into the transactionterminal (105) to initiate the transaction.

In one embodiment, the account information (142) can be entered directlyinto the transaction terminal (105) to make payment from the consumeraccount (146), without having to physically present the accountidentification device (141). When a transaction is initiated withoutphysically presenting an account identification device (141), thetransaction is classified as a “card-not-present” (CNP) transaction.

In general, the issuer processor (145) may control more than oneconsumer account (146); the acquirer processor (147) may control morethan one merchant account (148); and the transaction handler (103) isconnected between a plurality of issuer processors (e.g., 145) and aplurality of acquirer processors (e.g., 147). An entity (e.g., bank) mayoperate both an issuer processor (145) and an acquirer processor (147).

In one embodiment, the transaction handler (103), the issuer processor(145), the acquirer processor (147), the transaction terminal (105), theportal (143), and other devices and/or services accessing the portal(143) are connected via communications networks, such as local areanetworks, cellular telecommunications networks, wireless wide areanetworks, wireless local area networks, an intranet, and Internet.Dedicated communication channels may be used between the transactionhandler (103) and the issuer processor (145), between the transactionhandler (103) and the acquirer processor (147), and/or between theportal (143) and the transaction handler (103).

In FIG. 4, the transaction handler (103) uses the data warehouse (149)to store the records about the transactions, such as the transactionrecords (301) or transaction data.

Typically, the transaction handler (103) is implemented using a powerfulcomputer, or cluster of computers functioning as a unit, controlled byinstructions stored on a computer readable medium. The transactionhandler (103) is configured to support and deliver authorizationservices, exception file services, and clearing and settlement services.The transaction handler (103) has a subsystem to process authorizationrequests and another subsystem to perform clearing and settlementservices. The transaction handler (103) is configured to processdifferent types of transactions, such credit card transactions, debitcard transactions, prepaid card transactions, and other types ofcommercial transactions. The transaction handler (103) interconnects theissuer processors (e.g., 145) and the acquirer processor (e.g., 147) tofacilitate payment communications.

In FIG. 4, the transaction terminal (105) is configured to submit theauthorized transactions to the acquirer processor (147) for settlement.The amount for the settlement may be different from the amount specifiedin the authorization request. The transaction handler (103) is coupledbetween the issuer processor (145) and the acquirer processor (147) tofacilitate the clearing and settling of the transaction. Clearingincludes the exchange of financial information between the issuerprocessor (145) and the acquirer processor (147); and settlementincludes the exchange of funds.

In FIG. 4, the issuer processor (145) is configured to provide funds tomake payments on behalf of the consumer account (146). The acquirerprocessor (147) is to receive the funds on behalf of the merchantaccount (148). The issuer processor (145) and the acquirer processor(147) communicate with the transaction handler (103) to coordinate thetransfer of funds for the transaction. The funds can be transferredelectronically.

The transaction terminal (105) may submit a transaction directly forsettlement, without having to separately submit an authorizationrequest.

In one embodiment, the portal (143) provides transaction basedstatistics, such as indicators for retail spending monitoring,indicators for merchant benchmarking, industry/market segmentation,indicators of spending patterns, etc. Further examples can be found inU.S. Pat. App. Pub. No. 2009/0048884, and entitled “MerchantBenchmarking Tool,” the disclosure of which application is herebyincorporated herein by reference.

Transaction Terminal

FIG. 5 illustrates a transaction terminal according to one embodiment.The transaction terminal (105) illustrated in FIG. 5 can be used invarious systems discussed in connection with other figures of thepresent disclosure. In FIG. 5, the transaction terminal (105) isconfigured to interact with an account identification device (141) toobtain account information (142) about the consumer account (146).

In one embodiment, the transaction terminal (105) includes a memory(167) coupled to the processor (151), which controls the operations of areader (163), an input device (153), an output device (165) and anetwork interface (161). The memory (167) may store instructions for theprocessor (151) and/or data, such as an identification that isassociated with the merchant account (148).

In one embodiment, the reader (163) includes a magnetic strip reader. Inanother embodiment, the reader (163) includes a contactless reader, suchas a radio frequency identification (RFID) reader, a near fieldcommunications (NFC) device configured to read data via magnetic fieldcoupling (in accordance with ISO standard 14443/NFC), a Bluetoothtransceiver, a WiFi transceiver, an infrared transceiver, a laserscanner, etc.

In one embodiment, the input device (153) includes key buttons that canbe used to enter the account information (142) directly into thetransaction terminal (105) without the physical presence of the accountidentification device (141). The input device (153) can be configured toprovide further information to initiate a transaction, such as apersonal identification number (PIN), password, zip code, etc. that maybe used to access the account identification device (141), or incombination with the account information (142) obtained from the accountidentification device (141).

In one embodiment, the output device (165) may include a display, aspeaker, and/or a printer to present information, such as the result ofan authorization request, a receipt for the transaction, anadvertisement, etc.

In one embodiment, the network interface (161) is configured tocommunicate with the acquirer processor (147) via a telephoneconnection, an Internet connection, or a dedicated data communicationchannel.

In one embodiment, the instructions stored in the memory (167) areconfigured at least to cause the transaction terminal (105) to send anauthorization request message to the acquirer processor (147) toinitiate a transaction. The transaction terminal (105) may or may notsend a separate request for the clearing and settling of thetransaction. The instructions stored in the memory (167) are alsoconfigured to cause the transaction terminal (105) to perform othertypes of functions discussed in this description.

In one embodiment, a transaction terminal (105) may have fewercomponents than those illustrated in FIG. 5. For example, in oneembodiment, the transaction terminal (105) is configured for“card-not-present” transactions; and the transaction terminal (105) doesnot have a reader (163).

In one embodiment, a transaction terminal (105) may have more componentsthan those illustrated in FIG. 5. For example, in one embodiment, thetransaction terminal (105) is an ATM machine, which includes componentsto dispense cash under certain conditions.

Account Identification Device

FIG. 6 illustrates an account identifying device according to oneembodiment. In FIG. 6, the account identification device (141) isconfigured to carry account information (142) that identifies theconsumer account (146).

In one embodiment, the account identification device (141) includes amemory (167) coupled to the processor (151), which controls theoperations of a communication device (159), an input device (153), anaudio device (157) and a display device (155). The memory (167) maystore instructions for the processor (151) and/or data, such as theaccount information (142) associated with the consumer account (146).

In one embodiment, the account information (142) includes an identifieridentifying the issuer (and thus the issuer processor (145)) among aplurality of issuers, and an identifier identifying the consumer accountamong a plurality of consumer accounts controlled by the issuerprocessor (145). The account information (142) may include an expirationdate of the account identification device (141), the name of theconsumer holding the consumer account (146), and/or an identifieridentifying the account identification device (141) among a plurality ofaccount identification devices associated with the consumer account(146).

In one embodiment, the account information (142) may further include aloyalty program account number, accumulated rewards of the consumer inthe loyalty program, an address of the consumer, a balance of theconsumer account (146), transit information (e.g., a subway or trainpass), access information (e.g., access badges), and/or consumerinformation (e.g., name, date of birth), etc.

In one embodiment, the memory includes a nonvolatile memory, such asmagnetic strip, a memory chip, a flash memory, a Read Only Memory (ROM),etc. to store the account information (142).

In one embodiment, the information stored in the memory (167) of theaccount identification device (141) may also be in the form of datatracks that are traditionally associated with credits cards. Such tracksinclude Track 1 and Track 2. Track 1 (“International Air TransportAssociation”) stores more information than Track 2, and contains thecardholder's name as well as the account number and other discretionarydata. Track 1 is sometimes used by airlines when securing reservationswith a credit card. Track 2 (“American Banking Association”) iscurrently most commonly used and is read by ATMs and credit cardcheckers. The ABA (American Banking Association) designed thespecifications of Track 1 and banks abide by it. It contains thecardholder's account number, encrypted PIN, and other discretionarydata.

In one embodiment, the communication device (159) includes asemiconductor chip to implement a transceiver for communication with thereader (163) and an antenna to provide and/or receive wireless signals.

In one embodiment, the communication device (159) is configured tocommunicate with the reader (163). The communication device (159) mayinclude a transmitter to transmit the account information (142) viawireless transmissions, such as radio frequency signals, magneticcoupling, or infrared, Bluetooth or WiFi signals, etc.

In one embodiment, the account identification device (141) is in theform of a mobile phone, personal digital assistant (PDA), etc. The inputdevice (153) can be used to provide input to the processor (151) tocontrol the operation of the account identification device (141); andthe audio device (157) and the display device (155) may present statusinformation and/or other information, such as advertisements or offers.The account identification device (141) may include further componentsthat are not shown in FIG. 6, such as a cellular communicationssubsystem.

In one embodiment, the communication device (159) may access the accountinformation (142) stored on the memory (167) without going through theprocessor (151).

In one embodiment, the account identification device (141) has fewercomponents than those illustrated in FIG. 6. For example, an accountidentification device (141) does not have the input device (153), theaudio device (157) and the display device (155) in one embodiment; andin another embodiment, an account identification device (141) does nothave components (151-159).

For example, in one embodiment, an account identification device (141)is in the form of a debit card, a credit card, a smartcard, or aconsumer device that has optional features such as magnetic strips, orsmartcards.

An example of an account identification device (141) is a magnetic stripattached to a plastic substrate in the form of a card. The magneticstrip is used as the memory (167) of the account identification device(141) to provide the account information (142). Consumer information,such as account number, expiration date, and consumer name may beprinted or embossed on the card. A semiconductor chip implementing thememory (167) and the communication device (159) may also be embedded inthe plastic card to provide account information (142) in one embodiment.In one embodiment, the account identification device (141) has thesemiconductor chip but not the magnetic strip.

In one embodiment, the account identification device (141) is integratedwith a security device, such as an access card, a radio frequencyidentification (RFID) tag, a security card, a transponder, etc.

In one embodiment, the account identification device (141) is a handheldand compact device. In one embodiment, the account identification device(141) has a size suitable to be placed in a wallet or pocket of theconsumer.

Some examples of an account identification device (141) include a creditcard, a debit card, a stored value device, a payment card, a gift card,a smartcard, a smart media card, a payroll card, a health care card, awrist band, a keychain device, a supermarket discount card, atransponder, and a machine readable medium containing accountinformation (142).

In one embodiment, a mobile phone is configured to sort payment cardsstored therein based on its location. After the mobile phone determinesits current location coordinates via GPS, the mobile phone determinesone or more parameters, such as the merchant category of paymenttransactions to be made at the current location. Based on the one ormore parameters determined from the location, the mobile phone applies aset of rules to adjust the order of the payment cards in a mobile walletimplemented in the mobile phone based on optimization of potentialrewards that are expected from the use of the payment cards. Forexample, the merchant category can be used to predict the loyaltyrewards resulting from using the respective payment cards in the mobilewallet; and the order of the payment cards stored in the mobile phonecan be adjusted to list the payment card that offers most rewards on thetop.

In one embodiment, a method implemented in a mobile device includes:storing, in the mobile device, data identifying a plurality of paymentaccounts, each respective payment account of which is associated with aloyalty program that provides loyalty benefits for payment transactionsmade in the respective payment account; determining, by the mobiledevice, a location of the mobile device at a time of the making apayment at a point of sales terminal; identifying, by the mobile device,a merchant category of the payment based on the location of the mobiledevice; applying, by the mobile device, a set of predetermined rulesbased at least in part on the merchant category to determine an order ofthe plurality of payment accounts to optimize loyalty benefits generatedfrom the payment; and processing, by the mobile device, the paymentbased on the order.

Hardware

FIG. 7 illustrates a data processing system according to one embodiment.While FIG. 7 illustrates various components of a computer system, it isnot intended to represent any particular architecture or manner ofinterconnecting the components. One embodiment may use other systemsthat have fewer or more components than those shown in FIG. 7.

In FIG. 7, the data processing system (170) includes an inter-connect(171) (e.g., bus and system core logic), which interconnects amicroprocessor(s) (173) and memory (167). The microprocessor (173) iscoupled to cache memory (179) in the example of FIG. 7.

In one embodiment, the inter-connect (171) interconnects themicroprocessor(s) (173) and the memory (167) together and alsointerconnects them to input/output (I/O) device(s) (175) via I/Ocontroller(s) (177). I/O devices (175) may include a display deviceand/or peripheral devices, such as mice, keyboards, modems, networkinterfaces, printers, scanners, video cameras and other devices known inthe art. In one embodiment, when the data processing system is a serversystem, some of the I/O devices (175), such as printers, scanners, mice,and/or keyboards, are optional.

In one embodiment, the inter-connect (171) includes one or more busesconnected to one another through various bridges, controllers and/oradapters. In one embodiment the I/O controllers (177) include a USB(Universal Serial Bus) adapter for controlling USB peripherals, and/oran IEEE-1394 bus adapter for controlling IEEE-1394 peripherals.

In one embodiment, the memory (167) includes one or more of: ROM (ReadOnly Memory), volatile RAM (Random Access Memory), and non-volatilememory, such as hard drive, flash memory, etc.

Volatile RAM is typically implemented as dynamic RAM (DRAM) whichrequires power continually in order to refresh or maintain the data inthe memory. Non-volatile memory is typically a magnetic hard drive, amagnetic optical drive, an optical drive (e.g., a DVD RAM), or othertype of memory system which maintains data even after power is removedfrom the system. The non-volatile memory may also be a random accessmemory.

The non-volatile memory can be a local device coupled directly to therest of the components in the data processing system. A non-volatilememory that is remote from the system, such as a network storage devicecoupled to the data processing system through a network interface suchas a modem or Ethernet interface, can also be used.

In this description, some functions and operations are described asbeing performed by or caused by software code to simplify description.However, such expressions are also used to specify that the functionsresult from execution of the code/instructions by a processor, such as amicroprocessor.

Alternatively, or in combination, the functions and operations asdescribed here can be implemented using special purpose circuitry, withor without software instructions, such as using Application-SpecificIntegrated Circuit (ASIC) or Field-Programmable Gate Array (FPGA).Embodiments can be implemented using hardwired circuitry withoutsoftware instructions, or in combination with software instructions.Thus, the techniques are limited neither to any specific combination ofhardware circuitry and software, nor to any particular source for theinstructions executed by the data processing system.

While one embodiment can be implemented in fully functioning computersand computer systems, various embodiments are capable of beingdistributed as a computing product in a variety of forms and are capableof being applied regardless of the particular type of machine orcomputer-readable media used to actually effect the distribution.

At least some aspects disclosed can be embodied, at least in part, insoftware. That is, the techniques may be carried out in a computersystem or other data processing system in response to its processor,such as a microprocessor, executing sequences of instructions containedin a memory, such as ROM, volatile RAM, non-volatile memory, cache or aremote storage device.

Routines executed to implement the embodiments may be implemented aspart of an operating system or a specific application, component,program, object, module or sequence of instructions referred to as“computer programs.” The computer programs typically include one or moreinstructions set at various times in various memory and storage devicesin a computer, and that, when read and executed by one or moreprocessors in a computer, cause the computer to perform operationsnecessary to execute elements involving the various aspects.

A machine readable medium can be used to store software and data whichwhen executed by a data processing system causes the system to performvarious methods. The executable software and data may be stored invarious places including for example ROM, volatile RAM, non-volatilememory and/or cache. Portions of this software and/or data may be storedin any one of these storage devices. Further, the data and instructionscan be obtained from centralized servers or peer to peer networks.Different portions of the data and instructions can be obtained fromdifferent centralized servers and/or peer to peer networks at differenttimes and in different communication sessions or in a same communicationsession. The data and instructions can be obtained in entirety prior tothe execution of the applications. Alternatively, portions of the dataand instructions can be obtained dynamically, just in time, when neededfor execution. Thus, it is not required that the data and instructionsbe on a machine readable medium in entirety at a particular instance oftime.

Examples of computer-readable media include but are not limited torecordable and non-recordable type media such as volatile andnon-volatile memory devices, read only memory (ROM), random accessmemory (RAM), flash memory devices, floppy and other removable disks,magnetic disk storage media, optical storage media (e.g., Compact DiskRead-Only Memory (CD ROMS), Digital Versatile Disks (DVDs), etc.), amongothers. The computer-readable media may store the instructions.

The instructions may also be embodied in digital and analogcommunication links for electrical, optical, acoustical or other formsof propagated signals, such as carrier waves, infrared signals, digitalsignals, etc. However, propagated signals, such as carrier waves,infrared signals, digital signals, etc. are not tangible machinereadable medium and are not configured to store instructions.

In general, a machine readable medium includes any mechanism thatprovides (i.e., stores and/or transmits) information in a formaccessible by a machine (e.g., a computer, network device, personaldigital assistant, manufacturing tool, any device with a set of one ormore processors, etc.).

In various embodiments, hardwired circuitry may be used in combinationwith software instructions to implement the techniques. Thus, thetechniques are neither limited to any specific combination of hardwarecircuitry and software nor to any particular source for the instructionsexecuted by the data processing system.

OTHER ASPECTS

The description and drawings are illustrative and are not to beconstrued as limiting. The present disclosure is illustrative ofinventive features to enable a person skilled in the art to make and usethe techniques. Various features, as described herein, should be used incompliance with all current and future rules, laws and regulationsrelated to privacy, security, permission, consent, authorization, andothers. Numerous specific details are described to provide a thoroughunderstanding. However, in certain instances, well known or conventionaldetails are not described in order to avoid obscuring the description.References to one or an embodiment in the present disclosure are notnecessarily references to the same embodiment; and, such references meanat least one.

The use of headings herein is merely provided for ease of reference, andshall not be interpreted in any way to limit this disclosure or thefollowing claims.

Reference to “one embodiment” or “an embodiment” means that a particularfeature, structure, or characteristic described in connection with theembodiment is included in at least one embodiment of the disclosure. Theappearances of the phrase “in one embodiment” in various places in thespecification are not necessarily all referring to the same embodiment,and are not necessarily all referring to separate or alternativeembodiments mutually exclusive of other embodiments. Moreover, variousfeatures are described which may be exhibited by one embodiment and notby others. Similarly, various requirements are described which may berequirements for one embodiment but not other embodiments. Unlessexcluded by explicit description and/or apparent incompatibility, anycombination of various features described in this description is alsoincluded here. For example, the features described above in connectionwith “in one embodiment” or “in some embodiments” can be all optionallyincluded in one implementation, except where the dependency of certainfeatures on other features, as apparent from the description, may limitthe options of excluding selected features from the implementation, andincompatibility of certain features with other features, as apparentfrom the description, may limit the options of including selectedfeatures together in the implementation.

The disclosures of the above discussed patent documents are herebyincorporated herein by reference.

In the foregoing specification, the disclosure has been described withreference to specific exemplary embodiments thereof. It will be evidentthat various modifications may be made thereto without departing fromthe broader spirit and scope as set forth in the following claims. Thespecification and drawings are, accordingly, to be regarded in anillustrative sense rather than a restrictive sense.

What is claimed is:
 1. A mobile device, comprising: a memory storing a plurality of data items; and at least one microprocessor coupled with the memory configured to: prior to a communication session with a transaction terminal: communicate a location of the mobile device to at least one server; receive, from the at least one server, a category associated with the location of the mobile device; and determine, based on the category, an order of the data items; and during the communication session, communicate at least one of the data items to the transaction terminal in accordance with the order of the data items determined based on the category.
 2. The mobile device of claim 1, wherein the mobile device communicates with the at least one server over internet; and the mobile device communicates with the transaction terminal via near field communication.
 3. The mobile device of claim 2, wherein communicating of the location of the mobile device to the at least one server causes the at least one server to determine the category associated with the location of the mobile device.
 4. The mobile device of claim 3, wherein the at least one server includes a geolocation server and an attribute server.
 5. The mobile device of claim 4, wherein the geolocation server maps the location of the mobile device to an address.
 6. The mobile device of claim 5, wherein the attribute server maps the address to the category.
 7. The mobile device of claim 6, wherein the memory further comprises a mobile wallet configured to make a payment with the transaction terminal using at least one of the plurality of data items.
 8. The mobile device of claim 7, wherein each of the plurality of data items is an account identifier of a payment account.
 9. The mobile device of claim 8, wherein payment accounts identified by the plurality of data items offer different benefits payment transactions associated with different categories; and the processor is further configured to determine the order from ranking potential benefits of the payment from using the payment accounts according to the category identified from the location of the mobile device.
 10. The mobile device of claim 1, further comprising a position determination device configured to determine the location of the mobile device.
 11. A method implemented by a mobile device, comprising: storing a plurality of data items; prior to a communication session between the mobile device and a transaction terminal: communicating a location of the mobile device to at least one server; receiving, from the at least one server, a category associated with the location of the mobile device; and determining, based on the category, an order of the data items; and during the communication session, communicating at least one of the data items to the transaction terminal in accordance with the order of the data items determined based on the category.
 12. The method of claim 11, further comprising determining, using a position determination device of the mobile device, the location of the mobile device.
 13. The method of claim 12, wherein the at least one server includes a geolocation server and an attribute server.
 14. The method of claim 13, wherein the geolocation server maps the location of the mobile device to a name.
 15. The method of claim 14, wherein the attribute server maps the name to the category.
 16. The method of claim 15, wherein the mobile device comprises a mobile wallet to make a payment with the transaction terminal using at least one of the plurality of data items.
 17. The method of claim 16, wherein each of the plurality of data items is an account identifier of a payment account.
 18. The method of claim 17, wherein payment accounts identified by the plurality of data items offer different benefits payment transactions associated with different categories; and wherein determining the order of the data items further comprises determining the order based on ranking potential benefits of the payment from using the payment accounts according to the category identified from the location of the mobile device.
 19. A non-transitory computer storage medium storing instructions configured to instruct a mobile device to perform a method, the method comprising: storing a plurality of data items; prior to a communication session between the mobile device and a transaction terminal: communicating a location of the mobile device to at least one server; receiving, from the at least one server, a category associated with the location of the mobile device; and determining, based on the category, an order of the data items; and during the communication session, communicating at least one of the data items to the transaction terminal in accordance with the order of the data items determined based on the category.
 20. The non-transitory computer storage medium of claim 19, wherein the mobile device communicates with the transaction terminal in the communication session using near field communication; and the mobile device communicates with the at least one server over internet. 